-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fleet] Add installed_kibana_space_id
to epm-packages
saved objects
#120517
[Fleet] Add installed_kibana_space_id
to epm-packages
saved objects
#120517
Conversation
epm-packages
saved objectsinstalled_kibana_space_id
to epm-packages
saved objects
447785b
to
a134122
Compare
Pinging @elastic/fleet (Team:Fleet) |
e798a83
to
774034f
Compare
774034f
to
befbc38
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
kbn-test changes LGTM
Yes this is expected for now, we will need some further work to display the assets in all spaces. |
befbc38
to
68abf5e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is looking great and seems to work as intended. Have a few questions before merging below.
I did retest the case I noticed was broken in #119527 (review) and it now appears to be fixed! ✅
68abf5e
to
ac5220c
Compare
💛 Build succeeded, but was flaky
Test Failures
Metrics [docs]Public APIs missing comments
Saved Objects .kibana field count
History
To update your PR or re-run it, just comment with: cc @hop-dev |
installed_kibana_space_id
to epm-packages
saved objectsinstalled_kibana_space_id
to epm-packages
saved objects
💔 Backport failed
To backport manually run: |
…ts (elastic#120517) # Conflicts: # x-pack/plugins/fleet/server/routes/package_policy/handlers.test.ts # x-pack/plugins/fleet/server/routes/preconfiguration/index.ts
… objects (#120517) (#121553) * [Fleet] Add `installed_kibana_space_id` to `epm-packages` saved objects (#120517) # Conflicts: # x-pack/plugins/fleet/server/routes/package_policy/handlers.test.ts # x-pack/plugins/fleet/server/routes/preconfiguration/index.ts * fix handler types Co-authored-by: Mark Hopkin <mark.hopkin@elastic.co> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Summary
Part of #74353.
Add the
installed_kibana_space_id
to theepm-packages
saved object type, and use this field when removing assets.This enables us to better handle integrations that have been installed in different spaces, previously if we installed an integration in the default space, then uninstalled it in a different space, the assets would not be deleted.
Manual tests:
Install a package in the default space
epm-packages
saved object hasinstalled_kibana_space_id
set to defaultInstall a package not in the default space e.g space2
epm-packages
saved object hasinstalled_kibana_space_id
set to space2